Skip to main content
Check and provide your planning data

BETA This is a new service – your feedback will help us to improve it.

Back to dataset table
East Hampshire District Council

Tree

There is a problem

  • 1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1051

reference
691-tree-1
name
1051
tree-preservation-order

undefined

691-tpo-1
uprn
address-text
point
POINT (-1.016854 50.882255)
geometry
MULTIPOLYGON (((-1.016783 50.882247,-1.016786 50.882261,-1.016796 50.882274,-1.016811 50.882284,-1.016831 50.882290,-1.016853 50.882293,-1.016875 50.882291,-1.016895 50.882285,-1.016911 50.882275,-1.016921 50.882262,-1.016925 50.882248,-1.016922 50.882235,-1.016912 50.882222,-1.016896 50.882212,-1.016877 50.882205,-1.016855 50.882203,-1.016833 50.882205,-1.016813 50.882211,-1.016797 50.882221,-1.016787 50.882233,-1.016783 50.882247)))
notes
felled-date
entry-date
2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

  1. Fix the errors indicated
  2. Use the check service to make sure the data meets the standard
  3. Publish the updated data on the endpoint URL